-
Notifications
You must be signed in to change notification settings - Fork 383
fix: extend filter path resolution to support at
/path
filters from extensions
#13067
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
at: pre-ast
filtersat
/path
filters from extensions
at
/path
filters from extensionsat
/path
filters from extensions
The "at" resolution actually happens after path resolution. Apply same as in resolveFilters() entryPoints definition
Could this be for 1.8? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good. We need to have folks testing it more extensively, but it's a necessary fix. Thank you!
Several extensions (including several of mines) needed this so I expect to be thoroughly tested in broader context. |
Enhance the
resolveFilterExtension()
function to handle filters from extensions specified withpath
andat
.Add tests to verify the correct resolution of filter paths (extension) from objects.
Fixes #11750 (
ERROR (src/resources/filters/./common/wrapped-filter.lua:200) cannot open <extension-name>: No such file or directory
)